Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91cb6e32b2a51e63a797c26ef01f575387b770a498f0b060865d7bacf6980559

Tx prefix hash: 6643eaf4e0eff2df2dadd59b177e2550cc4efc613e375d0cd0f0831274fa353e
Tx public key: d43d7f54866af17d05f31bf804584b7cb15d7cb86db75f9fdec3386e04f06ae9
Timestamp: 1733106906 Timestamp [UCT]: 2024-12-02 02:35:06 Age [y:d:h:m:s]: 00:121:03:33:38
Block: 1166121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86371 RingCT/type: yes/0
Extra: 01d43d7f54866af17d05f31bf804584b7cb15d7cb86db75f9fdec3386e04f06ae902110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a78b5579fb5be2d4ef5e9987b1d1eff933a71d904977c90888653aecf0d9db46 0.600000000000 1651798 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": 1166131, "vin": [ { "gen": { "height": 1166121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78b5579fb5be2d4ef5e9987b1d1eff933a71d904977c90888653aecf0d9db46" } } ], "extra": [ 1, 212, 61, 127, 84, 134, 106, 241, 125, 5, 243, 27, 248, 4, 88, 75, 124, 177, 93, 124, 184, 109, 183, 95, 159, 222, 195, 56, 110, 4, 240, 106, 233, 2, 17, 0, 0, 0, 10, 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