Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8896d2984533aa17ea3ee11f6deacef26b7052c22fbd7553b3ef082fa773c6b

Tx prefix hash: a53c69ea6a564b4a985fb3a37eea7d8d2d03a8c32460daef730027db8b812efb
Tx public key: fe59ba3e6e93c783addb04d7ed4aa75055ac4b61d4b921569ccff63c7fe9cc20
Timestamp: 1709621437 Timestamp [UCT]: 2024-03-05 06:50:37 Age [y:d:h:m:s]: 00:357:17:43:37
Block: 971518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255771 RingCT/type: yes/0
Extra: 01fe59ba3e6e93c783addb04d7ed4aa75055ac4b61d4b921569ccff63c7fe9cc200211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fd39bd6f34170e5530f59364cd8a10dfce263566ebded3b9ca59a1ac3042fc4 0.600000000000 1431415 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": 971528, "vin": [ { "gen": { "height": 971518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fd39bd6f34170e5530f59364cd8a10dfce263566ebded3b9ca59a1ac3042fc4" } } ], "extra": [ 1, 254, 89, 186, 62, 110, 147, 199, 131, 173, 219, 4, 215, 237, 74, 167, 80, 85, 172, 75, 97, 212, 185, 33, 86, 156, 207, 246, 60, 127, 233, 204, 32, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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