Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49dccb5458922d3bda79570ac76a2907e5ad9039cd6836ad97dee5edb1670b68

Tx prefix hash: d79a34df08e2d5e143029c9927d81b6067570a7bbc9a107f8efa9f3433690cf7
Tx public key: b198dda058fd3674027ef931dcd3bd1f743b09c83a8e2a643bf3b260a4acb0e0
Timestamp: 1724967163 Timestamp [UCT]: 2024-08-29 21:32:43 Age [y:d:h:m:s]: 00:273:07:57:29
Block: 1098730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195249 RingCT/type: yes/0
Extra: 01b198dda058fd3674027ef931dcd3bd1f743b09c83a8e2a643bf3b260a4acb0e0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68fca633378a6e49cb3ec2dc976f6989c1304bb5f48558841e3244ff65ad8cc7 0.600000000000 1574545 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": 1098740, "vin": [ { "gen": { "height": 1098730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68fca633378a6e49cb3ec2dc976f6989c1304bb5f48558841e3244ff65ad8cc7" } } ], "extra": [ 1, 177, 152, 221, 160, 88, 253, 54, 116, 2, 126, 249, 49, 220, 211, 189, 31, 116, 59, 9, 200, 58, 142, 42, 100, 59, 243, 178, 96, 164, 172, 176, 224, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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