Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c7bb4e8ee0c9460c884cd85ba53fa9acfb8db30c4e828be805b2909f7487b5

Tx prefix hash: 99f480c45f810c479270fd0b75bc3b6b72abdfc043b430a22339b386c6e08bcf
Tx public key: 93aac095d181fac93c6c3f18f95635c2ddfcf8b0a5885d0a5e24609e9553a21d
Timestamp: 1725194930 Timestamp [UCT]: 2024-09-01 12:48:50 Age [y:d:h:m:s]: 00:212:19:04:29
Block: 1100628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151923 RingCT/type: yes/0
Extra: 0193aac095d181fac93c6c3f18f95635c2ddfcf8b0a5885d0a5e24609e9553a21d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70153540872a5441a74c6001fba7ad08bf7d09e26dd74e6da88068069577a7f1 0.600000000000 1576607 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": 1100638, "vin": [ { "gen": { "height": 1100628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70153540872a5441a74c6001fba7ad08bf7d09e26dd74e6da88068069577a7f1" } } ], "extra": [ 1, 147, 170, 192, 149, 209, 129, 250, 201, 60, 108, 63, 24, 249, 86, 53, 194, 221, 252, 248, 176, 165, 136, 93, 10, 94, 36, 96, 158, 149, 83, 162, 29, 2, 17, 0, 0, 0, 5, 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