Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772dd0955af52d4080ffdf2c7d147c2a243a959486c62a0cfbf4d33ce2eeeaca

Tx prefix hash: 8a08b8ed2fbf31534ce6b431f1bb2f4b6a7c4b111505d7763d6ca6e395325c79
Tx public key: 2843336b80cdfed2bb3db191a66c56c93c2b22e49f66a397a950f9a03e30dab3
Timestamp: 1709363629 Timestamp [UCT]: 2024-03-02 07:13:49 Age [y:d:h:m:s]: 01:275:03:11:00
Block: 969381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455394 RingCT/type: yes/0
Extra: 012843336b80cdfed2bb3db191a66c56c93c2b22e49f66a397a950f9a03e30dab30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 135c8052df4cc8871cc563691dd326db581bafcc8b77b677d195f5945afc3b27 0.600000000000 1429210 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": 969391, "vin": [ { "gen": { "height": 969381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135c8052df4cc8871cc563691dd326db581bafcc8b77b677d195f5945afc3b27" } } ], "extra": [ 1, 40, 67, 51, 107, 128, 205, 254, 210, 187, 61, 177, 145, 166, 108, 86, 201, 60, 43, 34, 228, 159, 102, 163, 151, 169, 80, 249, 160, 62, 48, 218, 179, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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