Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db592d45f8c695b41436af71b1aa986c89bea527fb7cf980cf47178004dda147

Tx prefix hash: 10804b075f1fc2fcee834cd4df702592f2d42df11e00d21e5c8eec488b7d8eb7
Tx public key: 5712db2df2bdadb0c4d7b89173fa1a84ba44c712c4e874dfb705a2292b4497ec
Timestamp: 1710656009 Timestamp [UCT]: 2024-03-17 06:13:29 Age [y:d:h:m:s]: 01:017:20:16:09
Block: 980114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273701 RingCT/type: yes/0
Extra: 015712db2df2bdadb0c4d7b89173fa1a84ba44c712c4e874dfb705a2292b4497ec02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa65edda0ed570e6678fa343d3ba82765dd717b26032e176f2583beb44ac680e 0.600000000000 1440173 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": 980124, "vin": [ { "gen": { "height": 980114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa65edda0ed570e6678fa343d3ba82765dd717b26032e176f2583beb44ac680e" } } ], "extra": [ 1, 87, 18, 219, 45, 242, 189, 173, 176, 196, 215, 184, 145, 115, 250, 26, 132, 186, 68, 199, 18, 196, 232, 116, 223, 183, 5, 162, 41, 43, 68, 151, 236, 2, 17, 0, 0, 0, 7, 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