Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1610b763af2b4b1b0d13f6cb6d2e7483026c2feb4b61687e776201d8299c46

Tx prefix hash: 6da28ccdb618ef76b6cfbe3fdf66f040baa7390445f599047338ff8d298140bd
Tx public key: 78ff6212cc57537c5e54e3a03004ae4859e30fbd312c6f1fe383d9aba44de5de
Timestamp: 1704399999 Timestamp [UCT]: 2024-01-04 20:26:39 Age [y:d:h:m:s]: 01:053:14:47:08
Block: 928203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299407 RingCT/type: yes/0
Extra: 0178ff6212cc57537c5e54e3a03004ae4859e30fbd312c6f1fe383d9aba44de5de0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ef0938caabce61ccfb94a94ba480f066cf3d5c558e0c7a843375cd49e6d0e6f 0.600000000000 1386061 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": 928213, "vin": [ { "gen": { "height": 928203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ef0938caabce61ccfb94a94ba480f066cf3d5c558e0c7a843375cd49e6d0e6f" } } ], "extra": [ 1, 120, 255, 98, 18, 204, 87, 83, 124, 94, 84, 227, 160, 48, 4, 174, 72, 89, 227, 15, 189, 49, 44, 111, 31, 227, 131, 217, 171, 164, 77, 229, 222, 2, 17, 0, 0, 0, 1, 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