Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7beb5900e6b54fd0ff8a14da627517ab083027e21ff0648a4a3ed1161c9948d3

Tx prefix hash: c58d23bbd3e07e848a43be7bb51f701c93cd99dace567f6d32c1590288383d3a
Tx public key: d09ef4e2c1e41f83a8eb7c88af24bddf307774f60f00f3ba3aa3d436db6d3615
Timestamp: 1749543027 Timestamp [UCT]: 2025-06-10 08:10:27 Age [y:d:h:m:s]: 00:153:15:12:11
Block: 1301931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107472 RingCT/type: yes/0
Extra: 01d09ef4e2c1e41f83a8eb7c88af24bddf307774f60f00f3ba3aa3d436db6d3615021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651bd5d1e03b8ab38c0da5900830a5b05f21937146eec0a36591541f21f3c64a 0.600000000000 1789494 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": 1301941, "vin": [ { "gen": { "height": 1301931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651bd5d1e03b8ab38c0da5900830a5b05f21937146eec0a36591541f21f3c64a" } } ], "extra": [ 1, 208, 158, 244, 226, 193, 228, 31, 131, 168, 235, 124, 136, 175, 36, 189, 223, 48, 119, 116, 246, 15, 0, 243, 186, 58, 163, 212, 54, 219, 109, 54, 21, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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