Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 397e2da3315ecf5e3a9e654b7b89ccfc3f154d7a54e4e0ed97f0bfbd23d7d299

Tx prefix hash: 3dc182318b35cb7cdb3ad4ebd79e3d56accad0bddb3b2f87e7a4fa0541281957
Tx public key: f21e08b5d9e88fd177944abd08690ecdc91d1a4ba33c7e4971950e534e1fd4e4
Timestamp: 1722715834 Timestamp [UCT]: 2024-08-03 20:10:34 Age [y:d:h:m:s]: 00:203:13:45:49
Block: 1080062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145363 RingCT/type: yes/0
Extra: 01f21e08b5d9e88fd177944abd08690ecdc91d1a4ba33c7e4971950e534e1fd4e402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8a3a4dd8691a4e2e4c69b33e2d2cc41ec03b2faa380f9a874b28233467d29f8 0.600000000000 1553279 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": 1080072, "vin": [ { "gen": { "height": 1080062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8a3a4dd8691a4e2e4c69b33e2d2cc41ec03b2faa380f9a874b28233467d29f8" } } ], "extra": [ 1, 242, 30, 8, 181, 217, 232, 143, 209, 119, 148, 74, 189, 8, 105, 14, 205, 201, 29, 26, 75, 163, 60, 126, 73, 113, 149, 14, 83, 78, 31, 212, 228, 2, 17, 0, 0, 0, 3, 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