Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a40a10dd67e86df9cfd57d3ebeeeaa4b6dadf161112b91963d6d0d0071284c5

Tx prefix hash: 0c11121014b199e6aafee17a8cd7e0cb642e4447d3fa1db2abd938953099a90b
Tx public key: 38820ded4f531d26a33e9b8f5875d4972ddf0f12f6d533c9475e918e9649d87f
Timestamp: 1720603274 Timestamp [UCT]: 2024-07-10 09:21:14 Age [y:d:h:m:s]: 00:270:03:42:05
Block: 1062567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192996 RingCT/type: yes/0
Extra: 0138820ded4f531d26a33e9b8f5875d4972ddf0f12f6d533c9475e918e9649d87f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c032342593adb431c4859478b439193eb717966ad9f2dbe977dff7bfe43a1e7d 0.600000000000 1533072 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": 1062577, "vin": [ { "gen": { "height": 1062567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c032342593adb431c4859478b439193eb717966ad9f2dbe977dff7bfe43a1e7d" } } ], "extra": [ 1, 56, 130, 13, 237, 79, 83, 29, 38, 163, 62, 155, 143, 88, 117, 212, 151, 45, 223, 15, 18, 246, 213, 51, 201, 71, 94, 145, 142, 150, 73, 216, 127, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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