Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 527f08baeb9b4735a2eba67ff2d32e830e76697a4530198fdd997fa15c512a81

Tx prefix hash: 73dd0dbafdcc5d33c4c32364bd829d7192fb5dfc9d26f17989e09a451cf41429
Tx public key: f445c9e9084bae99fbc17d49de39b28c4fe3e5e04e7b8fb06a750353051cb666
Timestamp: 1734177415 Timestamp [UCT]: 2024-12-14 11:56:55 Age [y:d:h:m:s]: 00:135:02:35:36
Block: 1175001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96363 RingCT/type: yes/0
Extra: 01f445c9e9084bae99fbc17d49de39b28c4fe3e5e04e7b8fb06a750353051cb6660211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31e0391cd004f29eadf6cf89f3ad88320729780adb61e504960aecec810ec447 0.600000000000 1661222 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": 1175011, "vin": [ { "gen": { "height": 1175001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31e0391cd004f29eadf6cf89f3ad88320729780adb61e504960aecec810ec447" } } ], "extra": [ 1, 244, 69, 201, 233, 8, 75, 174, 153, 251, 193, 125, 73, 222, 57, 178, 140, 79, 227, 229, 224, 78, 123, 143, 176, 106, 117, 3, 83, 5, 28, 182, 102, 2, 17, 0, 0, 0, 6, 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