Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3219659fbd6d8990e70430b4c84071439210804de64ad0764e9463b6ca7ff10

Tx prefix hash: 1bc2676d2d5386a8307abb141b731ad948245d1ee5b49b9adab0edfa26decd0a
Tx public key: 15f5626272e42fb0827608654d9eb3fac1f44f09d6c8e2bcfb9ae529752321aa
Timestamp: 1697325642 Timestamp [UCT]: 2023-10-14 23:20:42 Age [y:d:h:m:s]: 01:138:14:28:55
Block: 869778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360057 RingCT/type: yes/0
Extra: 0115f5626272e42fb0827608654d9eb3fac1f44f09d6c8e2bcfb9ae529752321aa021100000006faf35c9c000000000000000000

1 output(s) for total of 0.805497973000 dcy

stealth address amount amount idx
00: 2bd3036412e28e93a3335e5775518bcf40ae434532640a0ab325d17b3103d564 0.805497973000 1324633 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": 869788, "vin": [ { "gen": { "height": 869778 } } ], "vout": [ { "amount": 805497973, "target": { "key": "2bd3036412e28e93a3335e5775518bcf40ae434532640a0ab325d17b3103d564" } } ], "extra": [ 1, 21, 245, 98, 98, 114, 228, 47, 176, 130, 118, 8, 101, 77, 158, 179, 250, 193, 244, 79, 9, 214, 200, 226, 188, 251, 154, 229, 41, 117, 35, 33, 170, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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