Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f808a71657c01bea46682ac4d710eed5a772643477dfcb1d752bc518889f38d

Tx prefix hash: cf893b0945c74deea2472da2307b9834534f2ea70a28ddd5c3bef24df11af9f0
Tx public key: 8337163d5ea4cca1ac18d7f618a5815f4538b19e4d351812e525ab2de8119681
Timestamp: 1708515847 Timestamp [UCT]: 2024-02-21 11:44:07 Age [y:d:h:m:s]: 01:097:21:40:22
Block: 962346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331049 RingCT/type: yes/0
Extra: 018337163d5ea4cca1ac18d7f618a5815f4538b19e4d351812e525ab2de811968102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d058f4cbdd149fa36b84a262e0aa24a09ec108bfe6f9e1f81ddd5fbfc5dce5 0.600000000000 1421979 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": 962356, "vin": [ { "gen": { "height": 962346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d058f4cbdd149fa36b84a262e0aa24a09ec108bfe6f9e1f81ddd5fbfc5dce5" } } ], "extra": [ 1, 131, 55, 22, 61, 94, 164, 204, 161, 172, 24, 215, 246, 24, 165, 129, 95, 69, 56, 177, 158, 77, 53, 24, 18, 229, 37, 171, 45, 232, 17, 150, 129, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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