Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513114b2c9764a42f64b1bec10dcc923d1dca38c98f438480824d20a233d505f

Tx prefix hash: c2bbc22904e05970a13d6d5a7f98e5e6418a831533fe5a04479631bedb985a84
Tx public key: 1b7e198d0586c2464629c3181de8a4dc686baedf30edbb5bcc52dc2ac1a84a68
Timestamp: 1749627957 Timestamp [UCT]: 2025-06-11 07:45:57 Age [y:d:h:m:s]: 00:152:13:48:25
Block: 1302620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106731 RingCT/type: yes/0
Extra: 011b7e198d0586c2464629c3181de8a4dc686baedf30edbb5bcc52dc2ac1a84a68021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e340e7b58db9fe245971ecb92527c4fa1222de38cae50b44c7928cb22b940475 0.600000000000 1790191 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": 1302630, "vin": [ { "gen": { "height": 1302620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e340e7b58db9fe245971ecb92527c4fa1222de38cae50b44c7928cb22b940475" } } ], "extra": [ 1, 27, 126, 25, 141, 5, 134, 194, 70, 70, 41, 195, 24, 29, 232, 164, 220, 104, 107, 174, 223, 48, 237, 187, 91, 204, 82, 220, 42, 193, 168, 74, 104, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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