Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa16937d6e12e308c7d626521f1268e67d4c5dd3781d23385ee16236260cb61e

Tx prefix hash: fb724f19be6f9ed72d995ff0de5961e88f5233d2927d48964170bbd09cd524c4
Tx public key: 456aae10a52ef22f408a0755d9c821b6e3b3dded7af51a602a921f53387c6d53
Timestamp: 1695185255 Timestamp [UCT]: 2023-09-20 04:47:35 Age [y:d:h:m:s]: 01:202:04:55:45
Block: 852019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405598 RingCT/type: yes/0
Extra: 01456aae10a52ef22f408a0755d9c821b6e3b3dded7af51a602a921f53387c6d530211000000214b8f5122000000000000000000

1 output(s) for total of 0.922374774000 dcy

stealth address amount amount idx
00: 3030223860d76b30791ec9bba60c8fb10078a2b651957061d9be7953db6eb968 0.922374774000 1305833 of 0

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": 852029, "vin": [ { "gen": { "height": 852019 } } ], "vout": [ { "amount": 922374774, "target": { "key": "3030223860d76b30791ec9bba60c8fb10078a2b651957061d9be7953db6eb968" } } ], "extra": [ 1, 69, 106, 174, 16, 165, 46, 242, 47, 64, 138, 7, 85, 217, 200, 33, 182, 227, 179, 221, 237, 122, 245, 26, 96, 42, 146, 31, 83, 56, 124, 109, 83, 2, 17, 0, 0, 0, 33, 75, 143, 81, 34, 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