Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cad339f0368a4a60d596e2718d0606a9d2b7b252791acae6f457b61c0cc7e99d

Tx prefix hash: ceb517f834a63867c9d047ef5e7f3f07ff1b891035c38bf2e1a77e317323ee66
Tx public key: d7bdd4c21d4626a05cd0817bff57bc35f210f569cd28ff8cc64438ead2d348f1
Timestamp: 1714659432 Timestamp [UCT]: 2024-05-02 14:17:12 Age [y:d:h:m:s]: 00:337:17:04:29
Block: 1013280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241410 RingCT/type: yes/0
Extra: 01d7bdd4c21d4626a05cd0817bff57bc35f210f569cd28ff8cc64438ead2d348f10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eff003741bc366b4177e41104305945f6d6380e3ba6df7e3a7d1388cf711d11a 0.600000000000 1476055 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": 1013290, "vin": [ { "gen": { "height": 1013280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eff003741bc366b4177e41104305945f6d6380e3ba6df7e3a7d1388cf711d11a" } } ], "extra": [ 1, 215, 189, 212, 194, 29, 70, 38, 160, 92, 208, 129, 123, 255, 87, 188, 53, 242, 16, 245, 105, 205, 40, 255, 140, 198, 68, 56, 234, 210, 211, 72, 241, 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