Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38d1ac8fc7b5e341891223ed51c67ab2ff24cf628769d825bee2ff7a206e993

Tx prefix hash: 16693107b5c2fe84890156e472cc92805a02bbc4bbbe1927fed4cb608c7719d8
Tx public key: 81e2e958768d6f603480ce040ccf3cb9c46eb53b1d9f2de022b3e6d7551f92d7
Timestamp: 1708109126 Timestamp [UCT]: 2024-02-16 18:45:26 Age [y:d:h:m:s]: 00:331:08:05:09
Block: 958971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237194 RingCT/type: yes/0
Extra: 0181e2e958768d6f603480ce040ccf3cb9c46eb53b1d9f2de022b3e6d7551f92d70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 283e3e4155fe32541b6f2ccc3054351c332e95bb04d1998fc1a64239ccf2d50e 0.600000000000 1418464 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": 958981, "vin": [ { "gen": { "height": 958971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "283e3e4155fe32541b6f2ccc3054351c332e95bb04d1998fc1a64239ccf2d50e" } } ], "extra": [ 1, 129, 226, 233, 88, 118, 141, 111, 96, 52, 128, 206, 4, 12, 207, 60, 185, 196, 110, 181, 59, 29, 159, 45, 224, 34, 179, 230, 215, 85, 31, 146, 215, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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