Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6a3b60eed91d01202cc693b92b949bfb9a68ad215e3af4fb2c12bdfceab91e

Tx prefix hash: 1969ff12b139006b2d0729dabd1f40edd1fcd33b6b8c6dacea2fe73ccd0ed3a1
Tx public key: 76dfc9cec778a8dc3277fe429f10623469e4a081592e8e9bd1a234e4953a3eb6
Timestamp: 1718224953 Timestamp [UCT]: 2024-06-12 20:42:33 Age [y:d:h:m:s]: 00:315:05:46:32
Block: 1042845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225284 RingCT/type: yes/0
Extra: 0176dfc9cec778a8dc3277fe429f10623469e4a081592e8e9bd1a234e4953a3eb60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fca94598c792662e0bace27b93e2cee7d7f042d10e78f119571c2ffbb13460a 0.600000000000 1511854 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": 1042855, "vin": [ { "gen": { "height": 1042845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fca94598c792662e0bace27b93e2cee7d7f042d10e78f119571c2ffbb13460a" } } ], "extra": [ 1, 118, 223, 201, 206, 199, 120, 168, 220, 50, 119, 254, 66, 159, 16, 98, 52, 105, 228, 160, 129, 89, 46, 142, 155, 209, 162, 52, 228, 149, 58, 62, 182, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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