Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6855fe08bbecd45b7cbba6988ca710a8a3aa13b4826f5e0656162cad09a50c0

Tx prefix hash: 3cf34a4452fc96f728cd8faf862fe565593b6ab18614cddcde6ab8b2455a693b
Tx public key: 614bb3fb638f654c0ae4bde563e79d5c7defcfeeb52274b884740930b16d590f
Timestamp: 1715500479 Timestamp [UCT]: 2024-05-12 07:54:39 Age [y:d:h:m:s]: 00:336:14:20:13
Block: 1020280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240589 RingCT/type: yes/0
Extra: 01614bb3fb638f654c0ae4bde563e79d5c7defcfeeb52274b884740930b16d590f021100000006679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f24feda031b9128198832374a25de4a88d995af651e67d51723e596e4d0c5842 0.600000000000 1484341 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": 1020290, "vin": [ { "gen": { "height": 1020280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f24feda031b9128198832374a25de4a88d995af651e67d51723e596e4d0c5842" } } ], "extra": [ 1, 97, 75, 179, 251, 99, 143, 101, 76, 10, 228, 189, 229, 99, 231, 157, 92, 125, 239, 207, 238, 181, 34, 116, 184, 132, 116, 9, 48, 177, 109, 89, 15, 2, 17, 0, 0, 0, 6, 103, 154, 138, 129, 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