Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d91c44ecbfc21dd7f2da40616313c5e27ef9376b58564011a5583258863f4f26

Tx prefix hash: d2e4464f91c7e08ec7d610acb620239d890bc3bcf5676b61cd7f8157c6c8bfff
Tx public key: 8b3acbbb9087daa4003a95028e5aa50b5c9b2f371be2f007bb77a1af4c90a82c
Timestamp: 1745101575 Timestamp [UCT]: 2025-04-19 22:26:15 Age [y:d:h:m:s]: 00:262:13:46:43
Block: 1265153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185454 RingCT/type: yes/0
Extra: 018b3acbbb9087daa4003a95028e5aa50b5c9b2f371be2f007bb77a1af4c90a82c0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 039b80efdc7e4001235f51984b52220ed28798dddee5f409d9db9929b6dbb239 0.600000000000 1752356 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": 1265163, "vin": [ { "gen": { "height": 1265153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "039b80efdc7e4001235f51984b52220ed28798dddee5f409d9db9929b6dbb239" } } ], "extra": [ 1, 139, 58, 203, 187, 144, 135, 218, 164, 0, 58, 149, 2, 142, 90, 165, 11, 92, 155, 47, 55, 27, 226, 240, 7, 187, 119, 161, 175, 76, 144, 168, 44, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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