Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e51aa4342c729e6e28873e0a132a62d8a5632b6c6d78bd9ebe0445b0ecac17

Tx prefix hash: 8212f42b5b999f250bff0c61b92ac5edf4c38c9235a32c351f0ec4f31d481c50
Tx public key: e8ce9de186756a66dd79a1b97972ea7d538600b662f3705bafb4b47b293191e7
Timestamp: 1718721457 Timestamp [UCT]: 2024-06-18 14:37:37 Age [y:d:h:m:s]: 00:271:20:47:54
Block: 1046956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194290 RingCT/type: yes/0
Extra: 01e8ce9de186756a66dd79a1b97972ea7d538600b662f3705bafb4b47b293191e702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e840a9d6ff66d35fb31e69561c5bdb98d5ee24059194c16642815c0f8c5be27b 0.600000000000 1516775 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": 1046966, "vin": [ { "gen": { "height": 1046956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e840a9d6ff66d35fb31e69561c5bdb98d5ee24059194c16642815c0f8c5be27b" } } ], "extra": [ 1, 232, 206, 157, 225, 134, 117, 106, 102, 221, 121, 161, 185, 121, 114, 234, 125, 83, 134, 0, 182, 98, 243, 112, 91, 175, 180, 180, 123, 41, 49, 145, 231, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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