Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd3969a43e47477f7e7c7284bda5d97a1b0c0ece91a2f89aa80cfb2fabea92b

Tx prefix hash: 799aaf3450e530b01e8f9570542de8d421bf65d2803a8918d526124168ddd02a
Tx public key: d00b23e3ccf27a005871ca6f4aa1e98d5e84a75cf58e74dc128e077d58cf1a2e
Timestamp: 1723787600 Timestamp [UCT]: 2024-08-16 05:53:20 Age [y:d:h:m:s]: 00:233:12:20:42
Block: 1088960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 166753 RingCT/type: yes/0
Extra: 01d00b23e3ccf27a005871ca6f4aa1e98d5e84a75cf58e74dc128e077d58cf1a2e

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e94bf5418b173b1f279b0d6bd6bf327287fca57765501f7ee14d8fd982de6d07 0.600000000000 1563579 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": 1088970, "vin": [ { "gen": { "height": 1088960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e94bf5418b173b1f279b0d6bd6bf327287fca57765501f7ee14d8fd982de6d07" } } ], "extra": [ 1, 208, 11, 35, 227, 204, 242, 122, 0, 88, 113, 202, 111, 74, 161, 233, 141, 94, 132, 167, 92, 245, 142, 116, 220, 18, 142, 7, 125, 88, 207, 26, 46 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8