Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454f836d424fec502a12f17ecfa2955584b5a00cb04fcb70202307d8fe86e2d6

Tx prefix hash: 5d7d55a97946b287409a475883b204ae0056c9e524873178f8d15c96e4ab2ccc
Tx public key: afaaf4b8c606eef6ec4be52e66c2040c01a8c109bbeb20742398a35563ef1c61
Timestamp: 1694631339 Timestamp [UCT]: 2023-09-13 18:55:39 Age [y:d:h:m:s]: 01:207:18:35:26
Block: 847426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409580 RingCT/type: yes/0
Extra: 01afaaf4b8c606eef6ec4be52e66c2040c01a8c109bbeb20742398a35563ef1c6102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.955269560000 dcy

stealth address amount amount idx
00: 1a5053cd8c05f5792bc7002c64e15a5db8f234a0c157b9102e65df1df69b9870 0.955269560000 1300946 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": 847436, "vin": [ { "gen": { "height": 847426 } } ], "vout": [ { "amount": 955269560, "target": { "key": "1a5053cd8c05f5792bc7002c64e15a5db8f234a0c157b9102e65df1df69b9870" } } ], "extra": [ 1, 175, 170, 244, 184, 198, 6, 238, 246, 236, 75, 229, 46, 102, 194, 4, 12, 1, 168, 193, 9, 187, 235, 32, 116, 35, 152, 163, 85, 99, 239, 28, 97, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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