Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7a0200ba39fed3b2c4bbbe4c284b3c42f6732a99fadfabe47bacaf159409b0

Tx prefix hash: 709a5408cfdbb374e5058f4e7de848c356b24e126fdba3a7826d3e380bbec392
Tx public key: 0d62ddfe5460ba60cc518347df7f2d6a1a151bb40716b89e417664b2d9e62420
Timestamp: 1694850746 Timestamp [UCT]: 2023-09-16 07:52:26 Age [y:d:h:m:s]: 01:203:06:34:21
Block: 849246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406352 RingCT/type: yes/0
Extra: 010d62ddfe5460ba60cc518347df7f2d6a1a151bb40716b89e417664b2d9e62420021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.942096783000 dcy

stealth address amount amount idx
00: 74eb8c1a7ccd1c8266167217ab0eb6d64406494e60d40719b5452747caec3af7 0.942096783000 1302896 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": 849256, "vin": [ { "gen": { "height": 849246 } } ], "vout": [ { "amount": 942096783, "target": { "key": "74eb8c1a7ccd1c8266167217ab0eb6d64406494e60d40719b5452747caec3af7" } } ], "extra": [ 1, 13, 98, 221, 254, 84, 96, 186, 96, 204, 81, 131, 71, 223, 127, 45, 106, 26, 21, 27, 180, 7, 22, 184, 158, 65, 118, 100, 178, 217, 230, 36, 32, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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