Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a60e7dc08e6978d88bce67f953850f5264d956e72660dc4cb74d6eb65be6bb

Tx prefix hash: fef91156d84f1d4695e112639a74ab4ddfbebf52a47b038f5f70d0253d3d6469
Tx public key: b3b043d07674a5c626641c097790ecd5c5500f0b55937bd5e81deeb62ef3ca01
Timestamp: 1729866057 Timestamp [UCT]: 2024-10-25 14:20:57 Age [y:d:h:m:s]: 00:088:21:30:49
Block: 1139307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63523 RingCT/type: yes/0
Extra: 01b3b043d07674a5c626641c097790ecd5c5500f0b55937bd5e81deeb62ef3ca010211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91c302091232556f82ebf2bc952c0c7998e7fe69e7014738844dd2c4a6a633cd 0.600000000000 1623094 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": 1139317, "vin": [ { "gen": { "height": 1139307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91c302091232556f82ebf2bc952c0c7998e7fe69e7014738844dd2c4a6a633cd" } } ], "extra": [ 1, 179, 176, 67, 208, 118, 116, 165, 198, 38, 100, 28, 9, 119, 144, 236, 213, 197, 80, 15, 11, 85, 147, 123, 213, 232, 29, 238, 182, 46, 243, 202, 1, 2, 17, 0, 0, 0, 4, 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