Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c1aede62f0bd33745ff084f82b5e950461d472e66faef30247141f2ad4c87e

Tx prefix hash: 3bd958228f6f068b3f03dd7a266cbdb67ee5b297157784ae41b9efdda3ae2c21
Tx public key: 72573af932d64fe915b4b32613383983c8c3e26cbbb0cd9403f0c560c76a91f5
Timestamp: 1729290950 Timestamp [UCT]: 2024-10-18 22:35:50 Age [y:d:h:m:s]: 00:149:12:52:31
Block: 1134579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106668 RingCT/type: yes/0
Extra: 0172573af932d64fe915b4b32613383983c8c3e26cbbb0cd9403f0c560c76a91f50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73aee25c6f7d8e4632be303fe80dfeeb4167dcbacd32cfc94257a4cb892e8adf 0.600000000000 1617902 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": 1134589, "vin": [ { "gen": { "height": 1134579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73aee25c6f7d8e4632be303fe80dfeeb4167dcbacd32cfc94257a4cb892e8adf" } } ], "extra": [ 1, 114, 87, 58, 249, 50, 214, 79, 233, 21, 180, 179, 38, 19, 56, 57, 131, 200, 195, 226, 108, 187, 176, 205, 148, 3, 240, 197, 96, 199, 106, 145, 245, 2, 17, 0, 0, 0, 6, 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