Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e100c6c3144aff57031290696283d2a126bbaf01b13d613fe1f721526d9455bb

Tx prefix hash: c3acc80f5b65d41f45a989d335984c87da01ad534ae6fac403a0399328228426
Tx public key: cb4b8b7b7b109d8f08e1455d94b91fb0157f5ceb6667155601c3b3dd2bf8ead8
Timestamp: 1730843035 Timestamp [UCT]: 2024-11-05 21:43:55 Age [y:d:h:m:s]: 00:064:22:15:41
Block: 1147357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46459 RingCT/type: yes/0
Extra: 01cb4b8b7b7b109d8f08e1455d94b91fb0157f5ceb6667155601c3b3dd2bf8ead8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 151c7a6bb542ed0d7e181e7386ad5b91a98282affc11bf23456ecbc6514065b5 0.600000000000 1632052 of 15

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": 1147367, "vin": [ { "gen": { "height": 1147357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "151c7a6bb542ed0d7e181e7386ad5b91a98282affc11bf23456ecbc6514065b5" } } ], "extra": [ 1, 203, 75, 139, 123, 123, 16, 157, 143, 8, 225, 69, 93, 148, 185, 31, 176, 21, 127, 92, 235, 102, 103, 21, 86, 1, 195, 179, 221, 43, 248, 234, 216, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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