Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec4c10998141733789d6acc3c78a412c76e900a9d94c2c23a48c4906e5bb114

Tx prefix hash: dc30b9ef398ae979ee6a73f4d825175a4ec2cffdb2a0ab208a1037d3f1850847
Tx public key: ddc6541b4daa01fec80371d13e1bc0708dfe4749ca79e8aa0c406e96f90f3ae5
Timestamp: 1724888602 Timestamp [UCT]: 2024-08-28 23:43:22 Age [y:d:h:m:s]: 00:218:01:47:32
Block: 1098080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155713 RingCT/type: yes/0
Extra: 01ddc6541b4daa01fec80371d13e1bc0708dfe4749ca79e8aa0c406e96f90f3ae502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ba9ac45680eaad5adc3d83dcba5b13f672d7d234806142a0927380c7721dba4 0.600000000000 1573675 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": 1098090, "vin": [ { "gen": { "height": 1098080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ba9ac45680eaad5adc3d83dcba5b13f672d7d234806142a0927380c7721dba4" } } ], "extra": [ 1, 221, 198, 84, 27, 77, 170, 1, 254, 200, 3, 113, 209, 62, 27, 192, 112, 141, 254, 71, 73, 202, 121, 232, 170, 12, 64, 110, 150, 249, 15, 58, 229, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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