Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 276fb050fbdf0d86dcf3abb43358cd3443c8bd5ce57083a947f52df8dd8b5714

Tx prefix hash: 7da51f1bff13c0e6b7883698a4d3a839453e3fb119769385cb1669e1aee9b18e
Tx public key: 4ee86ddad36ac9ee24794a05f248d74d2bef8d80329ddea78ce3acf290addcb5
Timestamp: 1747571261 Timestamp [UCT]: 2025-05-18 12:27:41 Age [y:d:h:m:s]: 00:142:16:52:40
Block: 1285593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99627 RingCT/type: yes/0
Extra: 014ee86ddad36ac9ee24794a05f248d74d2bef8d80329ddea78ce3acf290addcb50211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6188e75b60da2886e0ff7d5ae77394488d32935bf87d459fef7d59addd8b65f5 0.600000000000 1773058 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": 1285603, "vin": [ { "gen": { "height": 1285593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6188e75b60da2886e0ff7d5ae77394488d32935bf87d459fef7d59addd8b65f5" } } ], "extra": [ 1, 78, 232, 109, 218, 211, 106, 201, 238, 36, 121, 74, 5, 242, 72, 215, 77, 43, 239, 141, 128, 50, 157, 222, 167, 140, 227, 172, 242, 144, 173, 220, 181, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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