Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e24dcee7587e0d1819e36ddbe8b720956fbdffb6f2f2424f76b093053994c95

Tx prefix hash: be9108b63958791feb5a1c1001e43ec9743294826f7d941364bdd706a6ffbb39
Tx public key: 6fd1d5ff334df722cfb54939ecfa41d0e3a2491771348e1d401e42d90fce62a4
Timestamp: 1704921513 Timestamp [UCT]: 2024-01-10 21:18:33 Age [y:d:h:m:s]: 01:088:23:52:39
Block: 932530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324709 RingCT/type: yes/0
Extra: 016fd1d5ff334df722cfb54939ecfa41d0e3a2491771348e1d401e42d90fce62a40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 210dfac7076a0cc8eae707ae6ca7bd74f699e64562559e5173b1ae736f3644f2 0.600000000000 1390466 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": 932540, "vin": [ { "gen": { "height": 932530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "210dfac7076a0cc8eae707ae6ca7bd74f699e64562559e5173b1ae736f3644f2" } } ], "extra": [ 1, 111, 209, 213, 255, 51, 77, 247, 34, 207, 181, 73, 57, 236, 250, 65, 208, 227, 162, 73, 23, 113, 52, 142, 29, 64, 30, 66, 217, 15, 206, 98, 164, 2, 17, 0, 0, 0, 2, 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