Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2565efca055f77d2ffbecce5bc710286acdc4f1e285d2b82f4ace503ce6655ba

Tx prefix hash: 12a5bcd69075dca616539bbc1600aec37befc5af419d2955ed0b0415c627f90e
Tx public key: ea1b227e39dfa82a376e639293eae7801fdf2ab74c38ae968c809045f5d50fbe
Timestamp: 1737975542 Timestamp [UCT]: 2025-01-27 10:59:02 Age [y:d:h:m:s]: 00:144:17:57:07
Block: 1206189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103342 RingCT/type: yes/0
Extra: 01ea1b227e39dfa82a376e639293eae7801fdf2ab74c38ae968c809045f5d50fbe02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a467f24a3ed4d4570453360c3e8f4cba19a3856ad2a11a3303af61cbe80d0685 0.600000000000 1692892 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": 1206199, "vin": [ { "gen": { "height": 1206189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a467f24a3ed4d4570453360c3e8f4cba19a3856ad2a11a3303af61cbe80d0685" } } ], "extra": [ 1, 234, 27, 34, 126, 57, 223, 168, 42, 55, 110, 99, 146, 147, 234, 231, 128, 31, 223, 42, 183, 76, 56, 174, 150, 140, 128, 144, 69, 245, 213, 15, 190, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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