Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9448f377e8b7d5b85b15770c652256c30ea5cfa522f9365e6f0d6f870af03b84

Tx prefix hash: c0585d7175d21ca4862d9595aad29447e86a02af071a632597a8fbddbda8e0f1
Tx public key: 3075f215a7f404a58e78b7f0acd28430a02d05bf5166849edc03410f97e15963
Timestamp: 1712542029 Timestamp [UCT]: 2024-04-08 02:07:09 Age [y:d:h:m:s]: 00:320:20:42:21
Block: 995687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229405 RingCT/type: yes/0
Extra: 013075f215a7f404a58e78b7f0acd28430a02d05bf5166849edc03410f97e1596302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1331c4372a9fb45f2db1bc0a837275764af454bc3f9238a21aa1f9024423060f 0.600000000000 1456101 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": 995697, "vin": [ { "gen": { "height": 995687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1331c4372a9fb45f2db1bc0a837275764af454bc3f9238a21aa1f9024423060f" } } ], "extra": [ 1, 48, 117, 242, 21, 167, 244, 4, 165, 142, 120, 183, 240, 172, 210, 132, 48, 160, 45, 5, 191, 81, 102, 132, 158, 220, 3, 65, 15, 151, 225, 89, 99, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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