Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d292811c496f866177135a4d3555fad2957afaffe8f3f8922a18c001ae93f5c8

Tx prefix hash: a4df003553bf63244b9172cc31fa62503fca4231bbb9148c322c324cc4b8b0df
Tx public key: 52b8d1b83f995fc13a0de5f0353efb94915a9917e7b5658e47ceb711f8ca4718
Timestamp: 1727367666 Timestamp [UCT]: 2024-09-26 16:21:06 Age [y:d:h:m:s]: 01:042:00:29:22
Block: 1118637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288425 RingCT/type: yes/0
Extra: 0152b8d1b83f995fc13a0de5f0353efb94915a9917e7b5658e47ceb711f8ca4718021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40e34b7523172e968c41d1b04a9ec3cd7db51e242782df95b50a9cec630f51c1 0.600000000000 1599898 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": 1118647, "vin": [ { "gen": { "height": 1118637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40e34b7523172e968c41d1b04a9ec3cd7db51e242782df95b50a9cec630f51c1" } } ], "extra": [ 1, 82, 184, 209, 184, 63, 153, 95, 193, 58, 13, 229, 240, 53, 62, 251, 148, 145, 90, 153, 23, 231, 181, 101, 142, 71, 206, 183, 17, 248, 202, 71, 24, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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