Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b579ace21c3d1c0fadddfb84ee8f2a8c01ea31800270a308268a4c591a2b8b76

Tx prefix hash: ce95aea2b8038b23b1d096166224bd7d600c70d1ff2fcc8fcd61ed3267fa728f
Tx public key: da5d4659bee84f73500f113f926e4af88604fc3eeb207469fe3d1ba26fd86eeb
Timestamp: 1708553256 Timestamp [UCT]: 2024-02-21 22:07:36 Age [y:d:h:m:s]: 01:029:12:44:28
Block: 962656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282127 RingCT/type: yes/0
Extra: 01da5d4659bee84f73500f113f926e4af88604fc3eeb207469fe3d1ba26fd86eeb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d444c60ba52944be2c51c5d2752334949542582cddef43ee535a8dd0f4e28a 0.600000000000 1422327 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": 962666, "vin": [ { "gen": { "height": 962656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d444c60ba52944be2c51c5d2752334949542582cddef43ee535a8dd0f4e28a" } } ], "extra": [ 1, 218, 93, 70, 89, 190, 232, 79, 115, 80, 15, 17, 63, 146, 110, 74, 248, 134, 4, 252, 62, 235, 32, 116, 105, 254, 61, 27, 162, 111, 216, 110, 235, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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