Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a2a4a4dce6f12d68b89ea4812cb6815e4eb38af48fbc1c7ebf5221d1c0a9e56

Tx prefix hash: 077b5cec838fd0a08521e74d8b7daa5272c93f2d776e8f93ce56771e3a5adb81
Tx public key: c33bc52aa735293543f944eef632e266aec71b1e2b7421f60e10245201f3a81a
Timestamp: 1700959583 Timestamp [UTC]: 2023-11-26 00:46:23 Age [y:d:h:m:s]: 02:104:19:52:37
Block: 899689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594614 RingCT/type: yes/0
Extra: 01c33bc52aa735293543f944eef632e266aec71b1e2b7421f60e10245201f3a81a021100000002faf35c9c000000000000000000

1 output(s) for total of 0.000641145869 xmr

stealth address amount amount idx tag
00: 57b2e93e143bce44db4e3b39860daa063cffd721478515f2f8dc0ac66c48220c 0.000641145869 1356152 of 0 -

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 dinastycoin-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": 899699, "vin": [ { "gen": { "height": 899689 } } ], "vout": [ { "amount": 641145869, "target": { "key": "57b2e93e143bce44db4e3b39860daa063cffd721478515f2f8dc0ac66c48220c" } } ], "extra": [ 1, 195, 59, 197, 42, 167, 53, 41, 53, 67, 249, 68, 238, 246, 50, 226, 102, 174, 199, 27, 30, 43, 116, 33, 246, 14, 16, 36, 82, 1, 243, 168, 26, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369