Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff881b052e1194d7683872e9570fd736cb5df7cda608403fd0dac5829c4ea65

Tx prefix hash: 53041563b3bd137d49cca3c34cf34edcdbf7361852090ed424af1fc93873a37f
Tx public key: a7e2bbe1dcb10a8d15f3a9b04616b2c63820b0da51394213c6f602bd7a96816b
Timestamp: 1682022394 Timestamp [UCT]: 2023-04-20 20:26:34 Age [y:d:h:m:s]: 02:041:22:22:25
Block: 742950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552142 RingCT/type: yes/0
Extra: 01a7e2bbe1dcb10a8d15f3a9b04616b2c63820b0da51394213c6f602bd7a96816b021100000006b3164c24000000000000000000

1 output(s) for total of 2.119817388000 dcy

stealth address amount amount idx
00: fbad6930516ff7fe8c1895edd52698a011b27a882fddb6ccf144ab02106fa0e4 2.119817388000 1189979 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": 742960, "vin": [ { "gen": { "height": 742950 } } ], "vout": [ { "amount": 2119817388, "target": { "key": "fbad6930516ff7fe8c1895edd52698a011b27a882fddb6ccf144ab02106fa0e4" } } ], "extra": [ 1, 167, 226, 187, 225, 220, 177, 10, 141, 21, 243, 169, 176, 70, 22, 178, 198, 56, 32, 176, 218, 81, 57, 66, 19, 198, 246, 2, 189, 122, 150, 129, 107, 2, 17, 0, 0, 0, 6, 179, 22, 76, 36, 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