Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c569e240b1903c354361ab4f2394d731e9ad51ebf62decf89ca5bad17a47b894

Tx prefix hash: 9fae7c5273a9e2cddbb48b6ef544c77f0ab1aa64b61d7d9df36ca361d7bc1282
Tx public key: 316ba6be74df29c97f87df6ec8a19aac0311a2fe373789e6748b48066827e019
Timestamp: 1713686736 Timestamp [UCT]: 2024-04-21 08:05:36 Age [y:d:h:m:s]: 00:355:11:19:28
Block: 1005203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254139 RingCT/type: yes/0
Extra: 01316ba6be74df29c97f87df6ec8a19aac0311a2fe373789e6748b48066827e01902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 446b21d6d2933934f90084b20f292035f1145d3b2a4ff4d32d0c1f88a5abe903 0.600000000000 1465787 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": 1005213, "vin": [ { "gen": { "height": 1005203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446b21d6d2933934f90084b20f292035f1145d3b2a4ff4d32d0c1f88a5abe903" } } ], "extra": [ 1, 49, 107, 166, 190, 116, 223, 41, 201, 127, 135, 223, 110, 200, 161, 154, 172, 3, 17, 162, 254, 55, 55, 137, 230, 116, 139, 72, 6, 104, 39, 224, 25, 2, 17, 0, 0, 0, 2, 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