Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa900d07d050af4726593f9ee84092dbaf57600faa4c516fecec09329cf0fbc

Tx prefix hash: e3a3f36d91e54116d7901453cc590311b83a24c2475f704de24b4813bdc4d6b9
Tx public key: 83e8f6f0fa6cfb2b6d53ed1a57db31a21ddc41b5dec3872c693a07038119e3c4
Timestamp: 1721325928 Timestamp [UCT]: 2024-07-18 18:05:28 Age [y:d:h:m:s]: 01:125:02:29:36
Block: 1068557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347914 RingCT/type: yes/0
Extra: 0183e8f6f0fa6cfb2b6d53ed1a57db31a21ddc41b5dec3872c693a07038119e3c402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2224efd3b07b856610c905d42556c068471a987aa7a67ad7668b6ae3ef39ff4 0.600000000000 1539636 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": 1068567, "vin": [ { "gen": { "height": 1068557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2224efd3b07b856610c905d42556c068471a987aa7a67ad7668b6ae3ef39ff4" } } ], "extra": [ 1, 131, 232, 246, 240, 250, 108, 251, 43, 109, 83, 237, 26, 87, 219, 49, 162, 29, 220, 65, 181, 222, 195, 135, 44, 105, 58, 7, 3, 129, 25, 227, 196, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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