Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406d346194ab08479cc641a679d3fba9e592e5d3e9f841aed7223d3fb09131a2

Tx prefix hash: c34401b81ff69aa6f5c09ad62d35729887baa45cbf0983ef5fbdc7e514536f16
Tx public key: c950b5f3996ef5314ae88f93ccfe54a301819cc3771aa34625d6e3acd52c5711
Timestamp: 1732682194 Timestamp [UCT]: 2024-11-27 04:36:34 Age [y:d:h:m:s]: 00:202:21:50:01
Block: 1162599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144757 RingCT/type: yes/0
Extra: 01c950b5f3996ef5314ae88f93ccfe54a301819cc3771aa34625d6e3acd52c571102110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db86d75fe447b4529f7d582e13b4bb0a0d058c1c1334bfa8461eafd31bae0ce1 0.600000000000 1648256 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": 1162609, "vin": [ { "gen": { "height": 1162599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db86d75fe447b4529f7d582e13b4bb0a0d058c1c1334bfa8461eafd31bae0ce1" } } ], "extra": [ 1, 201, 80, 181, 243, 153, 110, 245, 49, 74, 232, 143, 147, 204, 254, 84, 163, 1, 129, 156, 195, 119, 26, 163, 70, 37, 214, 227, 172, 213, 44, 87, 17, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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