Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46c677b9e4c070233db373b12b724d5a5d43ac9c49419963ccca058ec61a16f

Tx prefix hash: 25e448511266b4849df07d4a6bd76cc40c095983d3832ee69bd4cf971eb18afa
Tx public key: 6d4a626d64d18d9a3b30d0713449a5f5b302f8c8d64a5c4f536a6004912cc206
Timestamp: 1703689207 Timestamp [UCT]: 2023-12-27 15:00:07 Age [y:d:h:m:s]: 01:316:22:54:43
Block: 922332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485358 RingCT/type: yes/0
Extra: 016d4a626d64d18d9a3b30d0713449a5f5b302f8c8d64a5c4f536a6004912cc20602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f95045b84a7f24771558c3773843ab5ebc066b27ec9277479c09e765a01a5b7e 0.600000000000 1380028 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": 922342, "vin": [ { "gen": { "height": 922332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f95045b84a7f24771558c3773843ab5ebc066b27ec9277479c09e765a01a5b7e" } } ], "extra": [ 1, 109, 74, 98, 109, 100, 209, 141, 154, 59, 48, 208, 113, 52, 73, 165, 245, 179, 2, 248, 200, 214, 74, 92, 79, 83, 106, 96, 4, 145, 44, 194, 6, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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