Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a1608141b07ee4ecbc4be952ed78284bdc4dbf882cd625bdc4b817c8ee2e76

Tx prefix hash: 4ecfe0fc3290b6ed384c05391935fe985f82472c4ad5e01c72cc4618446b8117
Tx public key: 0c0b9084b7cecbf6f6cbdd5adc117e63b6d5ef7f40d6a6e5d88c4014c1719a94
Timestamp: 1683794168 Timestamp [UCT]: 2023-05-11 08:36:08 Age [y:d:h:m:s]: 01:242:08:16:01
Block: 757639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434653 RingCT/type: yes/0
Extra: 010c0b9084b7cecbf6f6cbdd5adc117e63b6d5ef7f40d6a6e5d88c4014c1719a94021100000003faf35c9c000000000000000000

1 output(s) for total of 1.895080549000 dcy

stealth address amount amount idx
00: ef3440661e27e3b1aaef91573d71017f4c7ba3f23890b364a1ba7e6d091a9ce3 1.895080549000 1206094 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": 757649, "vin": [ { "gen": { "height": 757639 } } ], "vout": [ { "amount": 1895080549, "target": { "key": "ef3440661e27e3b1aaef91573d71017f4c7ba3f23890b364a1ba7e6d091a9ce3" } } ], "extra": [ 1, 12, 11, 144, 132, 183, 206, 203, 246, 246, 203, 221, 90, 220, 17, 126, 99, 182, 213, 239, 127, 64, 214, 166, 229, 216, 140, 64, 20, 193, 113, 154, 148, 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