Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d51c4124cfc4d6c0e4c25037ab9cd040f54e92bf59f2aa513d5f4ddf40e7ac42

Tx prefix hash: 00532939fa0209dcbb3775e02fe7021417b5c83e327b1ee9f86102a4b1742320
Tx public key: d566f2a69f48deccac35a753760def366f6b0ce0ae58b2811e5099868d720407
Timestamp: 1582433757 Timestamp [UCT]: 2020-02-23 04:55:57 Age [y:d:h:m:s]: 04:309:17:18:15
Block: 70573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114005 RingCT/type: yes/0
Extra: 01d566f2a69f48deccac35a753760def366f6b0ce0ae58b2811e5099868d72040702110000000256c366d3000000000000000000

1 output(s) for total of 358.250983566000 dcy

stealth address amount amount idx
00: 1061de84fe789516a87812c5ea98c71d96ca14c3b624e9ae33121bc0b6b96eef 358.250983566000 130419 of 0

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": 70583, "vin": [ { "gen": { "height": 70573 } } ], "vout": [ { "amount": 358250983566, "target": { "key": "1061de84fe789516a87812c5ea98c71d96ca14c3b624e9ae33121bc0b6b96eef" } } ], "extra": [ 1, 213, 102, 242, 166, 159, 72, 222, 204, 172, 53, 167, 83, 118, 13, 239, 54, 111, 107, 12, 224, 174, 88, 178, 129, 30, 80, 153, 134, 141, 114, 4, 7, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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