Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 10afacf9fae102607c3b4a3ca49ae901c4b558ee9a530a90ea459ed9659f69e4

Tx prefix hash: 6573c748a858de3f7c037cc8cbf7ce880991e11ad871244593560f4565672693
Tx public key: dea6f8804129cfbab2fc16aa5f1024d3685a08cc9f83f7666d982c0178cad10e
Timestamp: 1631563093 Timestamp [UCT]: 2021-09-13 19:58:13 Age [y:d:h:m:s]: 03:113:04:22:38
Block: 333137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 856527 RingCT/type: yes/0
Extra: 01dea6f8804129cfbab2fc16aa5f1024d3685a08cc9f83f7666d982c0178cad10e02110000001437cb3088000000000000000000

1 output(s) for total of 48.326664146000 dcy

stealth address amount amount idx
00: 421f34ad20d2a1f7cbcb6737090d4dc53b9c1399d7dce3db5083dd25421384a5 48.326664146000 687584 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 333147, "vin": [ { "gen": { "height": 333137 } } ], "vout": [ { "amount": 48326664146, "target": { "key": "421f34ad20d2a1f7cbcb6737090d4dc53b9c1399d7dce3db5083dd25421384a5" } } ], "extra": [ 1, 222, 166, 248, 128, 65, 41, 207, 186, 178, 252, 22, 170, 95, 16, 36, 211, 104, 90, 8, 204, 159, 131, 247, 102, 109, 152, 44, 1, 120, 202, 209, 14, 2, 17, 0, 0, 0, 20, 55, 203, 48, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8