Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f061e7a9f5a4128453ff35810d9df9941679835b038a75c5b36f1f5cb672c13

Tx prefix hash: 4dad1bbfc46ea86c13c4b132d566c4e71a98051931ae2ae699c18917a140e82d
Tx public key: b81343b77a1b8239fb971d7d2fbdc5fefed43cda828c518535312348911916eb
Timestamp: 1734539096 Timestamp [UCT]: 2024-12-18 16:24:56 Age [y:d:h:m:s]: 01:005:01:56:42
Block: 1178010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262026 RingCT/type: yes/0
Extra: 01b81343b77a1b8239fb971d7d2fbdc5fefed43cda828c518535312348911916eb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 710e6cc13e3d1a4f6fdc06abffd89a3b334a8dc66f0739c848c1c17edeed9658 0.600000000000 1664393 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": 1178020, "vin": [ { "gen": { "height": 1178010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "710e6cc13e3d1a4f6fdc06abffd89a3b334a8dc66f0739c848c1c17edeed9658" } } ], "extra": [ 1, 184, 19, 67, 183, 122, 27, 130, 57, 251, 151, 29, 125, 47, 189, 197, 254, 254, 212, 60, 218, 130, 140, 81, 133, 53, 49, 35, 72, 145, 25, 22, 235, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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