Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cbbd489a24bff3f81c18a608b20edbe3f4461b7ec1416f514c95b3225f490d3

Tx prefix hash: bdf10a1206f6ab91be9e69d51878916353010c6f264f5586c2eadce98664429b
Tx public key: 08419de7e8ea0e7d89053c9595cfeb7d7c88cfcd557bfb6a9d4b4e7aaa331197
Timestamp: 1715729262 Timestamp [UCT]: 2024-05-14 23:27:42 Age [y:d:h:m:s]: 00:334:23:27:00
Block: 1022147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239430 RingCT/type: yes/0
Extra: 0108419de7e8ea0e7d89053c9595cfeb7d7c88cfcd557bfb6a9d4b4e7aaa33119702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fc6628e9af8b67ba3a63d87ef1d73bea4087a5774372693b7c8265cfa8d8283 0.600000000000 1486664 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": 1022157, "vin": [ { "gen": { "height": 1022147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fc6628e9af8b67ba3a63d87ef1d73bea4087a5774372693b7c8265cfa8d8283" } } ], "extra": [ 1, 8, 65, 157, 231, 232, 234, 14, 125, 137, 5, 60, 149, 149, 207, 235, 125, 124, 136, 207, 205, 85, 123, 251, 106, 157, 75, 78, 122, 170, 51, 17, 151, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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