Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde787f13511a21ee52d5bc2b3ef2f23b8d132d1e203e554fced735d8756cb0b

Tx prefix hash: 52c3c56d2d1c3df72fffd1f93fece5e084bed0a510ca056b0f0e1181da0ef40a
Tx public key: 66c7fd6a9255914eda8be0e9d9429a15bcc506488828311c4ceed40cd5a45616
Timestamp: 1746536078 Timestamp [UCT]: 2025-05-06 12:54:38 Age [y:d:h:m:s]: 00:237:18:00:21
Block: 1277031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167681 RingCT/type: yes/0
Extra: 0166c7fd6a9255914eda8be0e9d9429a15bcc506488828311c4ceed40cd5a456160211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3de9452e7e144e169eed95a18e20f0d28e4e4ca199e02ae2d8db9868d625a112 0.600000000000 1764382 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": 1277041, "vin": [ { "gen": { "height": 1277031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3de9452e7e144e169eed95a18e20f0d28e4e4ca199e02ae2d8db9868d625a112" } } ], "extra": [ 1, 102, 199, 253, 106, 146, 85, 145, 78, 218, 139, 224, 233, 217, 66, 154, 21, 188, 197, 6, 72, 136, 40, 49, 28, 76, 238, 212, 12, 213, 164, 86, 22, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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