Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a074c72666a3e2d6fe444c50f5216722f1dd402631740c7f0b3c52da0be9cd58

Tx prefix hash: 950497979f20431405a79da582192e26cacf816088092c042e28bc042130f37b
Tx public key: f1c84f6d7a19debbf964ea7f6cc436ccfaa5f4f328f6cde288714b9a66ca5d9d
Timestamp: 1730040254 Timestamp [UCT]: 2024-10-27 14:44:14 Age [y:d:h:m:s]: 00:010:18:00:59
Block: 1140759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7654 RingCT/type: yes/0
Extra: 01f1c84f6d7a19debbf964ea7f6cc436ccfaa5f4f328f6cde288714b9a66ca5d9d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a78c2fb92ed86c067e75598cb32196dfbb622f6990c605cbd8281e0d26316fa6 0.600000000000 1624562 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": 1140769, "vin": [ { "gen": { "height": 1140759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78c2fb92ed86c067e75598cb32196dfbb622f6990c605cbd8281e0d26316fa6" } } ], "extra": [ 1, 241, 200, 79, 109, 122, 25, 222, 187, 249, 100, 234, 127, 108, 196, 54, 204, 250, 165, 244, 243, 40, 246, 205, 226, 136, 113, 75, 154, 102, 202, 93, 157, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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