Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19778d7d783252bdeca32bdc2d93e472d770e95e9db760e6a1f715f695034b52

Tx prefix hash: 5d3325005f6d5bdecd61fdc417e7ee8a612d0a92fd127fa4cb51015ce005791e
Tx public key: 2b2ee15e32a909f45475988f4773810a11edf83f6706bf6591bccef22b39ea0a
Timestamp: 1728830462 Timestamp [UCT]: 2024-10-13 14:41:02 Age [y:d:h:m:s]: 00:152:07:16:06
Block: 1130765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108634 RingCT/type: yes/0
Extra: 012b2ee15e32a909f45475988f4773810a11edf83f6706bf6591bccef22b39ea0a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13f25914a4e2c594c75bbac93bfe73dc01a3483a9d56e13d78d33d659b019ef3 0.600000000000 1613644 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": 1130775, "vin": [ { "gen": { "height": 1130765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13f25914a4e2c594c75bbac93bfe73dc01a3483a9d56e13d78d33d659b019ef3" } } ], "extra": [ 1, 43, 46, 225, 94, 50, 169, 9, 244, 84, 117, 152, 143, 71, 115, 129, 10, 17, 237, 248, 63, 103, 6, 191, 101, 145, 188, 206, 242, 43, 57, 234, 10, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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