Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add798386cce0217e3aa9e25efd54a3219a176bcbb110b8ce16f6bcc9fd2041d

Tx prefix hash: ebfc6382de88cc11d5b8f51a37205cf186280cece017e5c7694beb8f2ad0b8af
Tx public key: fe8cb18095ba5ac4932302bf16eb2e9bbe1a7cb716da896b76e1fb303b12ecc4
Timestamp: 1745786624 Timestamp [UCT]: 2025-04-27 20:43:44 Age [y:d:h:m:s]: 00:205:23:08:19
Block: 1270830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144911 RingCT/type: yes/0
Extra: 01fe8cb18095ba5ac4932302bf16eb2e9bbe1a7cb716da896b76e1fb303b12ecc40211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d79ef25dec87186b9a6add8a87f0119133f6a1ad2135e620866472be873818a 0.600000000000 1758075 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": 1270840, "vin": [ { "gen": { "height": 1270830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d79ef25dec87186b9a6add8a87f0119133f6a1ad2135e620866472be873818a" } } ], "extra": [ 1, 254, 140, 177, 128, 149, 186, 90, 196, 147, 35, 2, 191, 22, 235, 46, 155, 190, 26, 124, 183, 22, 218, 137, 107, 118, 225, 251, 48, 59, 18, 236, 196, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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