Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f0fd47a8f06bd1b319cec4affefca767ee9b1a3a443d7a1f62ca36a9968946c

Tx prefix hash: 4b983a9c239af202d0213b8e2ea94f7a50bd47ff98e6d04f69d76ab427eb25b6
Tx public key: 645db553ceb7645bfdc3a9455d8c8d597d0aea27dc99222214488fec8489fb21
Timestamp: 1735673163 Timestamp [UCT]: 2024-12-31 19:26:03 Age [y:d:h:m:s]: 00:304:04:49:00
Block: 1187360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214915 RingCT/type: yes/0
Extra: 01645db553ceb7645bfdc3a9455d8c8d597d0aea27dc99222214488fec8489fb21021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d377bc1b68d7d0336abd6d5160520db427a29cdcaa64e0f4ac3cf2facbe10503 0.600000000000 1673849 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": 1187370, "vin": [ { "gen": { "height": 1187360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d377bc1b68d7d0336abd6d5160520db427a29cdcaa64e0f4ac3cf2facbe10503" } } ], "extra": [ 1, 100, 93, 181, 83, 206, 183, 100, 91, 253, 195, 169, 69, 93, 140, 141, 89, 125, 10, 234, 39, 220, 153, 34, 34, 20, 72, 143, 236, 132, 137, 251, 33, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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