Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c7038c1582da51132690cf1ece57e2a70775b5a3788610e5755e77c8e35f42

Tx prefix hash: f5351c949ac2d6e96da9a5a95830e71d8d7c5cced9fea09dac0d5640f4fac2df
Tx public key: 2d5a31c166b86023c00992da9ce58a3b590725758d4cc43dd2db70373c00a2b4
Timestamp: 1738929808 Timestamp [UCT]: 2025-02-07 12:03:28 Age [y:d:h:m:s]: 00:243:15:40:28
Block: 1214063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171842 RingCT/type: yes/0
Extra: 012d5a31c166b86023c00992da9ce58a3b590725758d4cc43dd2db70373c00a2b40211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdc81002bbeacdc346bf36cf1dfb47141c6a0a593499b3ca1c0ec925b51d14ab 0.600000000000 1700848 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": 1214073, "vin": [ { "gen": { "height": 1214063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc81002bbeacdc346bf36cf1dfb47141c6a0a593499b3ca1c0ec925b51d14ab" } } ], "extra": [ 1, 45, 90, 49, 193, 102, 184, 96, 35, 192, 9, 146, 218, 156, 229, 138, 59, 89, 7, 37, 117, 141, 76, 196, 61, 210, 219, 112, 55, 60, 0, 162, 180, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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