Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fab96b08558d831df58d779f2126d7be75a7f5f0d24b3d5bc3aeabd4a8b39d

Tx prefix hash: 45b7e208d85162f15598d49b086ca4971dc1b73359ceb195c6f521284e36932f
Tx public key: c9980eb6eb24cfc4fc738ad968e05754641988a54241d44cef13a66ae7e4ea85
Timestamp: 1720813014 Timestamp [UCT]: 2024-07-12 19:36:54 Age [y:d:h:m:s]: 00:199:00:12:29
Block: 1064303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142134 RingCT/type: yes/0
Extra: 01c9980eb6eb24cfc4fc738ad968e05754641988a54241d44cef13a66ae7e4ea85021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec89f02274b2e3f619874dd3d8a171a6621fd6f8e453939f497934e22a9b6632 0.600000000000 1534828 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": 1064313, "vin": [ { "gen": { "height": 1064303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec89f02274b2e3f619874dd3d8a171a6621fd6f8e453939f497934e22a9b6632" } } ], "extra": [ 1, 201, 152, 14, 182, 235, 36, 207, 196, 252, 115, 138, 217, 104, 224, 87, 84, 100, 25, 136, 165, 66, 65, 212, 76, 239, 19, 166, 106, 231, 228, 234, 133, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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