Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb20d84439a85a76bbdac79e1398b92ec2dc997f25573db635acba227e2422e0

Tx prefix hash: 38b0a3a01bde3eae43e90a182ba37e72e946daabbbedcdaa98ba691f2eb7388c
Tx public key: 2340b7e8439716857a515a2b4aa2b612f5b307f5fc800ca30ea8a2cbd01553e5
Timestamp: 1717568530 Timestamp [UCT]: 2024-06-05 06:22:10 Age [y:d:h:m:s]: 00:345:14:11:00
Block: 1037402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247005 RingCT/type: yes/0
Extra: 012340b7e8439716857a515a2b4aa2b612f5b307f5fc800ca30ea8a2cbd01553e502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19f8a1baff7ffba52d830fa05172156a4e3a7272247e2cacf57187ad263b55ef 0.600000000000 1505933 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": 1037412, "vin": [ { "gen": { "height": 1037402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19f8a1baff7ffba52d830fa05172156a4e3a7272247e2cacf57187ad263b55ef" } } ], "extra": [ 1, 35, 64, 183, 232, 67, 151, 22, 133, 122, 81, 90, 43, 74, 162, 182, 18, 245, 179, 7, 245, 252, 128, 12, 163, 14, 168, 162, 203, 208, 21, 83, 229, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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