Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070c4aad5c8379c2c40071fea487f85fb0efd1cadf4246e9978bbd6e17a2fcee

Tx prefix hash: 5899b78930bcc1dd9cb280b34a3429ebaf28fdf5f79d0c32c5651f364274c4d7
Tx public key: f9dff2e02a8214eab019dfae03d14eb9ceb82ceb0c1c0680b142179d0effc24f
Timestamp: 1710799718 Timestamp [UTC]: 2024-03-18 22:08:38 Age [y:d:h:m:s]: 01:344:17:15:01
Block: 981297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504768 RingCT/type: yes/0
Extra: 01f9dff2e02a8214eab019dfae03d14eb9ceb82ceb0c1c0680b142179d0effc24f0211000000060011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 34d57bca5517ac48a71f6adf7afabe510a35a2a58d7e85dc5f5400e19a55792b 0.000600000000 1441392 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 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": 981307, "vin": [ { "gen": { "height": 981297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d57bca5517ac48a71f6adf7afabe510a35a2a58d7e85dc5f5400e19a55792b" } } ], "extra": [ 1, 249, 223, 242, 224, 42, 130, 20, 234, 176, 25, 223, 174, 3, 209, 78, 185, 206, 184, 44, 235, 12, 28, 6, 128, 177, 66, 23, 157, 14, 255, 194, 79, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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