Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 348398863c96de4cefea35cae6c89764c7dade70c19b74db3aff8b910adfaf7b

Tx prefix hash: 8f31a691c3f863352d57f4cad39a21c1e5b0e5c6c6f60fb07eb3d38230cb7c68
Tx public key: 4ca29578a63efa8d189cc0979a91db5a7ada018c48ae8f1a01f68150ebc6c801
Timestamp: 1704163902 Timestamp [UCT]: 2024-01-02 02:51:42 Age [y:d:h:m:s]: 01:055:18:36:46
Block: 926260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300950 RingCT/type: yes/0
Extra: 014ca29578a63efa8d189cc0979a91db5a7ada018c48ae8f1a01f68150ebc6c8010211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2f82ce929f2e79eb9c60f16c351fb0e019514d9308794ae3a88120dfa54a669 0.600000000000 1384036 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": 926270, "vin": [ { "gen": { "height": 926260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f82ce929f2e79eb9c60f16c351fb0e019514d9308794ae3a88120dfa54a669" } } ], "extra": [ 1, 76, 162, 149, 120, 166, 62, 250, 141, 24, 156, 192, 151, 154, 145, 219, 90, 122, 218, 1, 140, 72, 174, 143, 26, 1, 246, 129, 80, 235, 198, 200, 1, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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