Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475c73f6fcd99e722e6e5cae248a81d6c1c89fb330e8fc8cbc9376927e7a2740

Tx prefix hash: c1a282f08f9f8676275a60aa3905224ba16dae78a861a101159e9adffefbb7ab
Tx public key: a0ac24cb3fc02cf4906ae52ca490808644407dc47455f23a285a5c4a2ebb059e
Timestamp: 1698632761 Timestamp [UCT]: 2023-10-30 02:26:01 Age [y:d:h:m:s]: 01:136:13:32:59
Block: 880622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358608 RingCT/type: yes/0
Extra: 01a0ac24cb3fc02cf4906ae52ca490808644407dc47455f23a285a5c4a2ebb059e021100000003faf35c9c000000000000000000

1 output(s) for total of 0.741538599000 dcy

stealth address amount amount idx
00: 9bc11d24e3d5760ee250fedf8ca944d6cbe654bd6a67bf4b70337677430ba4b0 0.741538599000 1336184 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": 880632, "vin": [ { "gen": { "height": 880622 } } ], "vout": [ { "amount": 741538599, "target": { "key": "9bc11d24e3d5760ee250fedf8ca944d6cbe654bd6a67bf4b70337677430ba4b0" } } ], "extra": [ 1, 160, 172, 36, 203, 63, 192, 44, 244, 144, 106, 229, 44, 164, 144, 128, 134, 68, 64, 125, 196, 116, 85, 242, 58, 40, 90, 92, 74, 46, 187, 5, 158, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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