Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2704d4155215a80bc80608a1d44ef96e2f36b9771c1ddc7e56af1c514206c6e3

Tx prefix hash: 068f0eda890a78373d06be3afdcac9b3d7c84562467ef815832b34a95f2974a3
Tx public key: 7e05a75cadbcc3a0609f9a3641b8be6411ad9f15c9f8f229e56b311e25db2376
Timestamp: 1724645721 Timestamp [UCT]: 2024-08-26 04:15:21 Age [y:d:h:m:s]: 00:230:06:12:05
Block: 1096067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164433 RingCT/type: yes/0
Extra: 017e05a75cadbcc3a0609f9a3641b8be6411ad9f15c9f8f229e56b311e25db237602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d54ae2d22ae5016052c93d354af0de5ce660bdd19a2592c94dd85a44f569d89 0.600000000000 1571254 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": 1096077, "vin": [ { "gen": { "height": 1096067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d54ae2d22ae5016052c93d354af0de5ce660bdd19a2592c94dd85a44f569d89" } } ], "extra": [ 1, 126, 5, 167, 92, 173, 188, 195, 160, 96, 159, 154, 54, 65, 184, 190, 100, 17, 173, 159, 21, 201, 248, 242, 41, 229, 107, 49, 30, 37, 219, 35, 118, 2, 17, 0, 0, 0, 1, 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