Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33295a912b61315bfdc2c420c97ae46286f77083100b5f37df776f251714f7c

Tx prefix hash: 7350f85259f6d97fa804b0eec7e70dcaf85af228bef79c3c2fba10aa2cb1e9bd
Tx public key: 588326e5f3eabe3b254746d5e357048a06b00c6601a780cf5cd7542ef21c0799
Timestamp: 1725023866 Timestamp [UCT]: 2024-08-30 13:17:46 Age [y:d:h:m:s]: 00:145:17:31:23
Block: 1099205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104196 RingCT/type: yes/0
Extra: 01588326e5f3eabe3b254746d5e357048a06b00c6601a780cf5cd7542ef21c079902110000001b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57a6e6000c4db72d5aeb2b6f7310fedfa22a8e4a51c579de6ffb98e85ba9f77a 0.600000000000 1575142 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": 1099215, "vin": [ { "gen": { "height": 1099205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57a6e6000c4db72d5aeb2b6f7310fedfa22a8e4a51c579de6ffb98e85ba9f77a" } } ], "extra": [ 1, 88, 131, 38, 229, 243, 234, 190, 59, 37, 71, 70, 213, 227, 87, 4, 138, 6, 176, 12, 102, 1, 167, 128, 207, 92, 215, 84, 46, 242, 28, 7, 153, 2, 17, 0, 0, 0, 27, 145, 225, 60, 4, 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