Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07c317f8401b9a7d179c37e397a1c8d04667de787a71fb2adfe05012590c3da4

Tx prefix hash: db2cc1ee833e1b59fbb420aaba61dcad1af3911204d22afd493203489a4007e5
Tx public key: 3bf354554cf839bdeab0d26c8f999e9ebff05e0c4fdff041e8313dd558d299b4
Timestamp: 1574675936 Timestamp [UCT]: 2019-11-25 09:58:56 Age [y:d:h:m:s]: 05:171:16:29:14
Block: 17072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1265368 RingCT/type: yes/0
Extra: 013bf354554cf839bdeab0d26c8f999e9ebff05e0c4fdff041e8313dd558d299b402110000000f0b4dd45a000000000000000000

1 output(s) for total of 538.808276504000 dcy

stealth address amount amount idx
00: 7a711adda22c5e2398571fd742b4a08bc20c06783c7f3fc13f85076fdafe83ad 538.808276504000 24418 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": 17082, "vin": [ { "gen": { "height": 17072 } } ], "vout": [ { "amount": 538808276504, "target": { "key": "7a711adda22c5e2398571fd742b4a08bc20c06783c7f3fc13f85076fdafe83ad" } } ], "extra": [ 1, 59, 243, 84, 85, 76, 248, 57, 189, 234, 176, 210, 108, 143, 153, 158, 158, 191, 240, 94, 12, 79, 223, 240, 65, 232, 49, 61, 213, 88, 210, 153, 180, 2, 17, 0, 0, 0, 15, 11, 77, 212, 90, 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