Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defe1a91dc0e89a4a107d442e3c6cf3ce324bd2e57ced3d1794ddcbf479c2a90

Tx prefix hash: 3020194f3c634f46f3588b1d42699ca6ef21477b6a9841d29f7b6453be3c068f
Tx public key: 1fb6b74327c61cf0ccf69f8a694da21340954823cda5869ce61df9a6dde899c9
Timestamp: 1741327563 Timestamp [UCT]: 2025-03-07 06:06:03 Age [y:d:h:m:s]: 00:244:16:10:36
Block: 1233914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172591 RingCT/type: yes/0
Extra: 011fb6b74327c61cf0ccf69f8a694da21340954823cda5869ce61df9a6dde899c9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f4ddeb7f662bf3f92bc9ef7e304a4d717791bc93b3bd7b743355c710e94475f 0.600000000000 1720839 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": 1233924, "vin": [ { "gen": { "height": 1233914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f4ddeb7f662bf3f92bc9ef7e304a4d717791bc93b3bd7b743355c710e94475f" } } ], "extra": [ 1, 31, 182, 183, 67, 39, 198, 28, 240, 204, 246, 159, 138, 105, 77, 162, 19, 64, 149, 72, 35, 205, 165, 134, 156, 230, 29, 249, 166, 221, 232, 153, 201, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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