Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50fa8a1b5f5bd0f90c38a738493ae4ba3c19f020281b91f090241a354bfdf35

Tx prefix hash: 57f91105c9d20fcfe4114819f3ef3c17816b8611109a81f7f8e1db3cac965349
Tx public key: a86e46888b213203ab33e56c4c3d99d5036cc2c20f9a09607c58120282c507b8
Timestamp: 1714996833 Timestamp [UCT]: 2024-05-06 12:00:33 Age [y:d:h:m:s]: 01:155:02:45:33
Block: 1016073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369442 RingCT/type: yes/0
Extra: 01a86e46888b213203ab33e56c4c3d99d5036cc2c20f9a09607c58120282c507b802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28ee9c06fb777aa23b1a58d7595b61b991baff3a3d272786eee253d502ddf184 0.600000000000 1479556 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": 1016083, "vin": [ { "gen": { "height": 1016073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ee9c06fb777aa23b1a58d7595b61b991baff3a3d272786eee253d502ddf184" } } ], "extra": [ 1, 168, 110, 70, 136, 139, 33, 50, 3, 171, 51, 229, 108, 76, 61, 153, 213, 3, 108, 194, 194, 15, 154, 9, 96, 124, 88, 18, 2, 130, 197, 7, 184, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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