Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a6a479fa225d63a6d7631ee6c6135e3ae065abd5fe35d301cc11133af5d7cc7

Tx prefix hash: b8222dccfca4cdaed7c7f51e677a07ff9febb7dbde4336f95a67fecc37710770
Tx public key: 940891a745959d1a8fd8d016ae1ff80d1912bd7d8738a13d672e362d4d90afe2
Timestamp: 1725560889 Timestamp [UCT]: 2024-09-05 18:28:09 Age [y:d:h:m:s]: 00:170:12:51:00
Block: 1103665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121669 RingCT/type: yes/0
Extra: 01940891a745959d1a8fd8d016ae1ff80d1912bd7d8738a13d672e362d4d90afe2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03296402ef31985287d993fe7de99cee5e3fefa254fc24f1a2b69b7452edd3da 0.600000000000 1580582 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": 1103675, "vin": [ { "gen": { "height": 1103665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03296402ef31985287d993fe7de99cee5e3fefa254fc24f1a2b69b7452edd3da" } } ], "extra": [ 1, 148, 8, 145, 167, 69, 149, 157, 26, 143, 216, 208, 22, 174, 31, 248, 13, 25, 18, 189, 125, 135, 56, 161, 61, 103, 46, 54, 45, 77, 144, 175, 226, 2, 17, 0, 0, 0, 7, 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