Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d576556fa6fe201a565791180298c827e72870835f70c1fe02c9d670780b45

Tx prefix hash: 45eb9e0262a1745f0a772fc19ea66b3d40c1a5f786108e3f405628581f1c269b
Tx public key: de3765d526336f0ac2225b22bba2eb6f676d8938f538b8721c3f501c8bda1f80
Timestamp: 1734110272 Timestamp [UCT]: 2024-12-13 17:17:52 Age [y:d:h:m:s]: 00:112:04:08:45
Block: 1174456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79930 RingCT/type: yes/0
Extra: 01de3765d526336f0ac2225b22bba2eb6f676d8938f538b8721c3f501c8bda1f800211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d939d8339f6dfc89cf6df498c7f58fbf05e4bd0e7b6637f1be2604c5900e19e2 0.600000000000 1660609 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": 1174466, "vin": [ { "gen": { "height": 1174456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d939d8339f6dfc89cf6df498c7f58fbf05e4bd0e7b6637f1be2604c5900e19e2" } } ], "extra": [ 1, 222, 55, 101, 213, 38, 51, 111, 10, 194, 34, 91, 34, 187, 162, 235, 111, 103, 109, 137, 56, 245, 56, 184, 114, 28, 63, 80, 28, 139, 218, 31, 128, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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