Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2759c67e3c266a70517febd1398137214e8adb52671e1064f3745edd94cd0d50

Tx prefix hash: 842329edd3a30962ba027fb611a9a002ee862034b279aac4849709b2fa86b573
Tx public key: 831efd4ac3871a8f3a9371bd90d4ca4d0d6cbc9acac0412e1a7ca7a918aa3235
Timestamp: 1704248766 Timestamp [UCT]: 2024-01-03 02:26:06 Age [y:d:h:m:s]: 00:316:23:39:34
Block: 926957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226966 RingCT/type: yes/0
Extra: 01831efd4ac3871a8f3a9371bd90d4ca4d0d6cbc9acac0412e1a7ca7a918aa32350211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68375972ce6ca209994f0df97b2e146ba018dff9617528ebf10a29d9e6f2e73a 0.600000000000 1384757 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": 926967, "vin": [ { "gen": { "height": 926957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68375972ce6ca209994f0df97b2e146ba018dff9617528ebf10a29d9e6f2e73a" } } ], "extra": [ 1, 131, 30, 253, 74, 195, 135, 26, 143, 58, 147, 113, 189, 144, 212, 202, 77, 13, 108, 188, 154, 202, 192, 65, 46, 26, 124, 167, 169, 24, 170, 50, 53, 2, 17, 0, 0, 0, 6, 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