Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cfdbe65c9c1449cff29000b5b51a760b4794808151cef6f4daca2f1ca8b9d71

Tx prefix hash: ace71a8dd9511e3d1260301afa0bee5fe94620e24eee2eb8ab931a83b39699f1
Tx public key: a415c802a9f351a5704c64fe2c376007c6b0cae43505cf921e6dff12daab8378
Timestamp: 1658527186 Timestamp [UCT]: 2022-07-22 21:59:46 Age [y:d:h:m:s]: 02:222:00:32:44
Block: 549549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 679829 RingCT/type: yes/0
Extra: 01a415c802a9f351a5704c64fe2c376007c6b0cae43505cf921e6dff12daab837802110000000bcb8520c2000000000000000000

1 output(s) for total of 9.270777697000 dcy

stealth address amount amount idx
00: 2f3101265621d73e170b613a635498015aa688dab9ed992af64f87fd2fa5039e 9.270777697000 980926 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": 549559, "vin": [ { "gen": { "height": 549549 } } ], "vout": [ { "amount": 9270777697, "target": { "key": "2f3101265621d73e170b613a635498015aa688dab9ed992af64f87fd2fa5039e" } } ], "extra": [ 1, 164, 21, 200, 2, 169, 243, 81, 165, 112, 76, 100, 254, 44, 55, 96, 7, 198, 176, 202, 228, 53, 5, 207, 146, 30, 109, 255, 18, 218, 171, 131, 120, 2, 17, 0, 0, 0, 11, 203, 133, 32, 194, 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