Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f199ed8fd146969411b6e08c67b977182d60f605a528702a1c1b07c0f15759

Tx prefix hash: cff200680c1213d3d866d720bc12d30020ce49e4b0f1b4427f3e5c649c38118f
Tx public key: a111cd3958351c469d40ccea3dfd170bb44294267e1a5c411bbd7e1d601ccbf0
Timestamp: 1744986858 Timestamp [UCT]: 2025-04-18 14:34:18 Age [y:d:h:m:s]: 00:215:23:48:05
Block: 1264203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152083 RingCT/type: yes/0
Extra: 01a111cd3958351c469d40ccea3dfd170bb44294267e1a5c411bbd7e1d601ccbf0021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d942c24c6949f3b24e629b273747f4b1a620d4c996a2f94fa61a2d0e62d9da0 0.600000000000 1751398 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": 1264213, "vin": [ { "gen": { "height": 1264203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d942c24c6949f3b24e629b273747f4b1a620d4c996a2f94fa61a2d0e62d9da0" } } ], "extra": [ 1, 161, 17, 205, 57, 88, 53, 28, 70, 157, 64, 204, 234, 61, 253, 23, 11, 180, 66, 148, 38, 126, 26, 92, 65, 27, 189, 126, 29, 96, 28, 203, 240, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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