Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81eb26963aac97a7c6470bfcde6f94bb4dc99788bb7c302bfd05c07789732006

Tx prefix hash: caf7101e6ce80fd9658268a09f1ca71015ef86a4b6441864a75957213f8bbeaa
Tx public key: 0076ec37bc54934c0bdcc1923d8c02544716b146e9cd9643a5b8f0b0165bd309
Timestamp: 1699273262 Timestamp [UCT]: 2023-11-06 12:21:02 Age [y:d:h:m:s]: 01:076:13:16:49
Block: 885719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316094 RingCT/type: yes/0
Extra: 010076ec37bc54934c0bdcc1923d8c02544716b146e9cd9643a5b8f0b0165bd309021100000004faf35c9c000000000000000000

1 output(s) for total of 0.713255744000 dcy

stealth address amount amount idx
00: 19db4a6be9a807101d1c883cfff17de80020f1ed5f56b9f1ab11f3c5ab0dbf28 0.713255744000 1341502 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": 885729, "vin": [ { "gen": { "height": 885719 } } ], "vout": [ { "amount": 713255744, "target": { "key": "19db4a6be9a807101d1c883cfff17de80020f1ed5f56b9f1ab11f3c5ab0dbf28" } } ], "extra": [ 1, 0, 118, 236, 55, 188, 84, 147, 76, 11, 220, 193, 146, 61, 140, 2, 84, 71, 22, 177, 70, 233, 205, 150, 67, 165, 184, 240, 176, 22, 91, 211, 9, 2, 17, 0, 0, 0, 4, 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