Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f932a6e72076c21680296b7e3229348be8bca1313c0511e6b500ff64b577db9c

Tx prefix hash: 319508b2b096f35a69a0b454301ad18df7c3e65f465f07e152b5bea282030487
Tx public key: b614614f048b822df467687aa20cd71f54398dec294a6c4d1f262470c64322d9
Timestamp: 1698237379 Timestamp [UCT]: 2023-10-25 12:36:19 Age [y:d:h:m:s]: 01:167:04:36:21
Block: 877351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380487 RingCT/type: yes/0
Extra: 01b614614f048b822df467687aa20cd71f54398dec294a6c4d1f262470c64322d9021100000002faf35c9c000000000000000000

1 output(s) for total of 0.760277167000 dcy

stealth address amount amount idx
00: cee17015aa3718622bc82bc547e824916ff1ee2c9bc9978e9f4cf1dc009e62f9 0.760277167000 1332725 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": 877361, "vin": [ { "gen": { "height": 877351 } } ], "vout": [ { "amount": 760277167, "target": { "key": "cee17015aa3718622bc82bc547e824916ff1ee2c9bc9978e9f4cf1dc009e62f9" } } ], "extra": [ 1, 182, 20, 97, 79, 4, 139, 130, 45, 244, 103, 104, 122, 162, 12, 215, 31, 84, 57, 141, 236, 41, 74, 108, 77, 31, 38, 36, 112, 198, 67, 34, 217, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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