Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ff5abe7a598d1e1f07b22d9cf239bf71ef852cb51d8410ec2c5f55fafca3ea

Tx prefix hash: 4b46c15ade27804afcd08b79844e6ebf25758ffccc14a9f9d179e986e1f79074
Tx public key: 727547ec9110f62ac41e8dd4c01af9b3fc7fc8ed16ae4ca4616fd4afe3e591bf
Timestamp: 1715336869 Timestamp [UCT]: 2024-05-10 10:27:49 Age [y:d:h:m:s]: 00:227:12:54:05
Block: 1018898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162880 RingCT/type: yes/0
Extra: 01727547ec9110f62ac41e8dd4c01af9b3fc7fc8ed16ae4ca4616fd4afe3e591bf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90be1d872c21cc81477c809dadf7cc63ed30912854c5d5d6db656dd4f7be66f1 0.600000000000 1482713 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": 1018908, "vin": [ { "gen": { "height": 1018898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90be1d872c21cc81477c809dadf7cc63ed30912854c5d5d6db656dd4f7be66f1" } } ], "extra": [ 1, 114, 117, 71, 236, 145, 16, 246, 42, 196, 30, 141, 212, 192, 26, 249, 179, 252, 127, 200, 237, 22, 174, 76, 164, 97, 111, 212, 175, 227, 229, 145, 191, 2, 17, 0, 0, 0, 1, 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