Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b66b5a489d2a6f84583cdaba53ee386754e4f3bf183bc41ce5398a57ba3e51

Tx prefix hash: c5150c43af93c4fdea91df9abf3f234d4c38456146ce58a497fc784e41aa2626
Tx public key: 836b6bdfd1afef9f73c8d8bcbe856f419ec9b3aabeb77f7c7df3d5d7730ddfef
Timestamp: 1736081434 Timestamp [UCT]: 2025-01-05 12:50:34 Age [y:d:h:m:s]: 00:085:08:01:42
Block: 1190755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60754 RingCT/type: yes/0
Extra: 01836b6bdfd1afef9f73c8d8bcbe856f419ec9b3aabeb77f7c7df3d5d7730ddfef021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5084ed43c2fd9ed4371de62e288a02addce0863a74592c84db4cce162559d212 0.600000000000 1677274 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": 1190765, "vin": [ { "gen": { "height": 1190755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5084ed43c2fd9ed4371de62e288a02addce0863a74592c84db4cce162559d212" } } ], "extra": [ 1, 131, 107, 107, 223, 209, 175, 239, 159, 115, 200, 216, 188, 190, 133, 111, 65, 158, 201, 179, 170, 190, 183, 127, 124, 125, 243, 213, 215, 115, 13, 223, 239, 2, 17, 0, 0, 0, 4, 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