Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1c683bd4640e3f6ac1dc8b814343e24880e2632db1c0a8ce823cadf2477ca5

Tx prefix hash: 26fb9c73f299b1aa27639dc4ff65194d87db6818908deef3ce547064825c0f0b
Tx public key: 235315047d6247386177c75c097a8ff8baa5f61d9d6f599ced71c436098aa93c
Timestamp: 1700972464 Timestamp [UCT]: 2023-11-26 04:21:04 Age [y:d:h:m:s]: 01:173:01:51:30
Block: 899799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384900 RingCT/type: yes/0
Extra: 01235315047d6247386177c75c097a8ff8baa5f61d9d6f599ced71c436098aa93c021100000013e6d27f9c000000000000000000

1 output(s) for total of 0.640608021000 dcy

stealth address amount amount idx
00: 407359dc7944a1fa3669ddb121d9b8ff12d2d3a2d6835a8bc8d335b4e1f1df4a 0.640608021000 1356262 of 0

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": 899809, "vin": [ { "gen": { "height": 899799 } } ], "vout": [ { "amount": 640608021, "target": { "key": "407359dc7944a1fa3669ddb121d9b8ff12d2d3a2d6835a8bc8d335b4e1f1df4a" } } ], "extra": [ 1, 35, 83, 21, 4, 125, 98, 71, 56, 97, 119, 199, 92, 9, 122, 143, 248, 186, 165, 246, 29, 157, 111, 89, 156, 237, 113, 196, 54, 9, 138, 169, 60, 2, 17, 0, 0, 0, 19, 230, 210, 127, 156, 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