Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7a2d41cb2166858da8b6c832a2e6af75751d4dce47b5555b85ba84ec4b7c56

Tx prefix hash: d628cf0f850c878803442c24e160550ba1491d84c057f5f162077972dd69b585
Tx public key: 0ab60d6cdde895d50ab05a6cd6b56bdb652bc26fea8fa74cfc201d92b4cac3c3
Timestamp: 1717973390 Timestamp [UCT]: 2024-06-09 22:49:50 Age [y:d:h:m:s]: 01:157:17:39:52
Block: 1040751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371306 RingCT/type: yes/0
Extra: 010ab60d6cdde895d50ab05a6cd6b56bdb652bc26fea8fa74cfc201d92b4cac3c30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a89ddd9e903209f7a32e032b7c41c9b83a43159bb086feca3430b45d8655a106 0.600000000000 1509412 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": 1040761, "vin": [ { "gen": { "height": 1040751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a89ddd9e903209f7a32e032b7c41c9b83a43159bb086feca3430b45d8655a106" } } ], "extra": [ 1, 10, 182, 13, 108, 221, 232, 149, 213, 10, 176, 90, 108, 214, 181, 107, 219, 101, 43, 194, 111, 234, 143, 167, 76, 252, 32, 29, 146, 180, 202, 195, 195, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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