Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b95b11b784d16d1b779276004e8fdbd1f5cd3854a50e067e6f85e12f02fa69e

Tx prefix hash: 52836beb28f42539695b90d6ac5797a9f658b73998520657b424d1fa3c0ec07e
Tx public key: a95b4ee02c0f76ad25f9cea83c08d4d6af34926f9135e04e495bdd2d12c1d9a5
Timestamp: 1729801525 Timestamp [UCT]: 2024-10-24 20:25:25 Age [y:d:h:m:s]: 00:161:13:56:52
Block: 1138778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115288 RingCT/type: yes/0
Extra: 01a95b4ee02c0f76ad25f9cea83c08d4d6af34926f9135e04e495bdd2d12c1d9a50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64932666bf5814e34c12cdb29e54916e52ea9efcc5c21a5cf5676a1210180181 0.600000000000 1622501 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": 1138788, "vin": [ { "gen": { "height": 1138778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64932666bf5814e34c12cdb29e54916e52ea9efcc5c21a5cf5676a1210180181" } } ], "extra": [ 1, 169, 91, 78, 224, 44, 15, 118, 173, 37, 249, 206, 168, 60, 8, 212, 214, 175, 52, 146, 111, 145, 53, 224, 78, 73, 91, 221, 45, 18, 193, 217, 165, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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