Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f48775d956ecc3614bd89e4cbee1523eeb904eb05b08d2397e922a012b0982

Tx prefix hash: bc1f5f8bac52e66d344b379ca23d535a3f07a175f334b6abd093410799e74b5d
Tx public key: 465fd72be18d9c957c6d7696a1052cdf55b36e5362f7a3a67184a43ceba61546
Timestamp: 1754832077 Timestamp [UCT]: 2025-08-10 13:21:17 Age [y:d:h:m:s]: 00:051:06:15:53
Block: 1344172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35750 RingCT/type: yes/0
Extra: 01465fd72be18d9c957c6d7696a1052cdf55b36e5362f7a3a67184a43ceba61546021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bf3ad40fbdaa1deaceb4860b950f6a591e452491ab85860ce3b258df8614972 0.600000000000 1832049 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": 1344182, "vin": [ { "gen": { "height": 1344172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf3ad40fbdaa1deaceb4860b950f6a591e452491ab85860ce3b258df8614972" } } ], "extra": [ 1, 70, 95, 215, 43, 225, 141, 156, 149, 124, 109, 118, 150, 161, 5, 44, 223, 85, 179, 110, 83, 98, 247, 163, 166, 113, 132, 164, 60, 235, 166, 21, 70, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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