Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b2c61837b821c3ba52c5c52073bfe12eb5204b6b461db6ec605a63740f7167

Tx prefix hash: 4a49501bab5dabf524dc8e8e0efdc60d938d744e7a993076260e4060a21b6095
Tx public key: da8e5c6bac951ae0cc3d017cf059fa09e7ac0f60bd51e9a14ce97e70d2f5810a
Timestamp: 1707303544 Timestamp [UCT]: 2024-02-07 10:59:04 Age [y:d:h:m:s]: 01:076:15:49:21
Block: 952291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315846 RingCT/type: yes/0
Extra: 01da8e5c6bac951ae0cc3d017cf059fa09e7ac0f60bd51e9a14ce97e70d2f5810a02110000000d10a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c97727143063015a944007e728a24f1913cae34d180f419076cc9c430d688f 0.600000000000 1411201 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": 952301, "vin": [ { "gen": { "height": 952291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c97727143063015a944007e728a24f1913cae34d180f419076cc9c430d688f" } } ], "extra": [ 1, 218, 142, 92, 107, 172, 149, 26, 224, 204, 61, 1, 124, 240, 89, 250, 9, 231, 172, 15, 96, 189, 81, 233, 161, 76, 233, 126, 112, 210, 245, 129, 10, 2, 17, 0, 0, 0, 13, 16, 161, 116, 143, 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