Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e646a1dfcf5f01b124bafb62472c06ecd45328be8ffb11c54aff39977b8b052f

Tx prefix hash: 5ef1bf8fa9e9ee9181809b850417b563ef21f0868d32587a1b923889f4477f73
Tx public key: 4bc50153fa7a39564206606b91b62c93a8a1d12719a777a858d0af07b2dceb70
Timestamp: 1705930942 Timestamp [UCT]: 2024-01-22 13:42:22 Age [y:d:h:m:s]: 01:073:08:00:54
Block: 940881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313511 RingCT/type: yes/0
Extra: 014bc50153fa7a39564206606b91b62c93a8a1d12719a777a858d0af07b2dceb7002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6215742c1dff3e67a741c962a3a0f3e5f0b9afb03b9c04b59e2a019a966aeb6a 0.600000000000 1399021 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": 940891, "vin": [ { "gen": { "height": 940881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6215742c1dff3e67a741c962a3a0f3e5f0b9afb03b9c04b59e2a019a966aeb6a" } } ], "extra": [ 1, 75, 197, 1, 83, 250, 122, 57, 86, 66, 6, 96, 107, 145, 182, 44, 147, 168, 161, 209, 39, 25, 167, 119, 168, 88, 208, 175, 7, 178, 220, 235, 112, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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