Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a41cedf17ae45b9dfc854aa4295d239451b4b6f2a3287d4bade28a6a67429a56

Tx prefix hash: 659f74c3abc9bc93115fde0cd25f350dbe5244e1f7d8928d384d2b6cc215f345
Tx public key: 38181dd01bfebbb302a441cf217f669110646d52aa78fc4ebcf46e9459efa42c
Timestamp: 1588516763 Timestamp [UCT]: 2020-05-03 14:39:23 Age [y:d:h:m:s]: 04:349:13:31:01
Block: 98346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164822 RingCT/type: yes/0
Extra: 0138181dd01bfebbb302a441cf217f669110646d52aa78fc4ebcf46e9459efa42c02110000000237fb5df4000000000000000000

1 output(s) for total of 289.827533544000 dcy

stealth address amount amount idx
00: bc27f1fa7ab623488369e99efb7979d3b81952ff8c648422fe3cd7845d9f6a2a 289.827533544000 173769 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": 98356, "vin": [ { "gen": { "height": 98346 } } ], "vout": [ { "amount": 289827533544, "target": { "key": "bc27f1fa7ab623488369e99efb7979d3b81952ff8c648422fe3cd7845d9f6a2a" } } ], "extra": [ 1, 56, 24, 29, 208, 27, 254, 187, 179, 2, 164, 65, 207, 33, 127, 102, 145, 16, 100, 109, 82, 170, 120, 252, 78, 188, 244, 110, 148, 89, 239, 164, 44, 2, 17, 0, 0, 0, 2, 55, 251, 93, 244, 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